home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Info-Mac 4
/
Info_Mac IV CD-ROM (Pacific HiTech Inc.)(August 1994).iso
/
Development
/
General
/
SC++ 7.0.2 Update
/
Release Notes
/
Visual Architect READ ME
< prev
Wrap
Text File
|
1994-05-19
|
8KB
|
216 lines
Visual Architect 7.0.1 READ ME
==============================
Copyright ©1994 Symantec Corporation. All Rights Reserved.
May 8, 1994
Font: Geneva 12
This file contains last minute corrections and additions pertaining
to the Visual Architect application that are not described in the
Visual Architect/THINK Class Library Guide.
Tutorial Errata
==============
The Beeper Tutorial (Chapter 5 of the Visual Architect/THINK Class
Library Guide) requires the following changes:
• On page 41, figure 4-5 should be:
• Also on page 41, Step 2 should read as follows:
2. In the New View dialog box, type BeeperDialog in the field Name,
select Modal Dialog from the View Kind popup, and click OK.
• On page 43, Step 1 should read as follows:
1. Choose the Edit Text tool from the Tool Palette. Note that the cursor
changes to a cross hair when it is over the dialog box. Click the cursor to
the right of the static text pane you just added, to position the edit text pane.
An edit text box appears. Now press Return or Enter to edit the defualt static
text. Type the number "2", and then type Enter a second time to finish
the edit task.
You can constrain the type of text the user is allowed to enter into the edit
text pane by selecting a special THINK Class Library class, as shown in the next
step. The edit text pane then becomes an instance of this class.
• In Chapter 6, the Process Monitor tutorial, p. 73: The first sentence of Step 2
should read:
2. Choose Pane Info from the Pane menu (Command-L), or double-click the button
pane.
Converting from Classy to Visual Architect
=======================================
Visual Architect can read existing Classy resource files, however a few steps
must be taken to properly convert all of the view information. These steps are:
1. Open the Classy Resource file using Visual Architect
2. For each view, do the following:
a. Open the view
b. Modify the view in some trivial way. The easiest thing is to do a Select All
(command-a) and then move all the panes one step to the left, and then back
one step to the right by pressing the left and right arrow keys, respectively
3. Select Save from the File menu to save the converted resource file
Common Mistakes
================
When working with Visual Architect, keep in mind that it creates two
"levels" of files for your application. All files that begin with "x_" are
files that are modified as needed by Visual Architect. You should NOT make
changes directly to any of the "x_" files, since Visual Architect will just
overwrite that file. Any user changes should always be in the upper level
files.
Automatic Window Closing
========================
Anytime that Visual Architect generates a file, it will check with the THINK
Project Manager to see if that file is open in the Editor. If it is, Visual
Architect will ask the THINK Project Manager to close the window. As a result,
you will notice from time to time that editor windows showing lower layer ("x_")
files are automatically closed during the generate phase of Visual Architect. When
the generate phase is complete, you can again open any lower layer files in the
THINK Project Manager's editor.
File IDs in the Application Info dialog
==================================
Visual Architect's Application Info dialog (opened by choosing Application from
the Edit menu) allows you to specify File IDs that the application will use. Keep in
mind that these IDs must be four character constants like 'doc1' or 'MyDc'. If you
don't enter four character, Visual Architect will display a validation dialog to
remind you.
Using Hierarchical Menus
========================
When you create a menu item that has a hierarchical submenu attached,
that menu item will have cmdNull assigned as its default command by
Visual Architect. Because of the way that the THINK Class Library enables
menus, this means that the menu item containing hierarchical items will
be disabled, even if some or all of the hierarchal items should be
enabled. To cause the menu item to be enabled, you need to create a dummy
command handled by the appropriate view or application class. Then assign
this command to the menu item containing the hierarchical menu.
For example, if there is to be a menu item called 'Foo' in the File menu
that has a hierarchic menu that should be enabled when the 'Main' document
is active, follow the following steps:
1. Create a new command named cmdDummyFoo
2. Set the In Class: pop up for the command to be CMain
3. Set the command action to "None"
Now the Foo menu item will be enabled any time a 'Main' document window
is the frontmost window.
Creating Multiple Columns for CArrayPane Derived Classes
=====================================================
When creating CArrayPane panes in Visual Architect, you cannot specify the
number of columns in the Pane Info dialog. To create a multi-column table,
you can use the following technique in your CArrayPane's GetFrom() member
function:
void MyArrayPane::GetFrom(
CStream &aStream)
{
// Get any additional data members for this class
// before calling the superclass GetFrom
/* Let superclass restore */
x_MyArrayPane::GetFrom(aStream);
// Next three lines of code set up a multicolumn table
DeleteCol(1,1); // One column is automatically created, we delete it here
// so that default column width will be honored
AddCol(someCols, -1); // someCols is the number of columns for your table
AddRow(someRows, -1); // someRows is the number of rows for your table
// Restore any subordinate objects below
}
Fixed in Visual Architect 7.0.1
=======================
• Cmd-U is now used exclusively for Bring Up To Date (like TPM)
instead of Underline.
• Balloon Help is now disabled in menu dialogs.
• The Tools menu is now deactivated when a TearoffMenu is in front.
• CPane height, width, hEncl and vEncl now show their correct values
when pane is enclosed in a scrollpane. This allows users to change
the pane size and offset.
• The Tools palette is now hidden and the Tools menu disabled when a
Pane Info window is frontmost.
• If you Generate All then Run, VA won't generate again.
• VA now asks TPM to close and mark changed all generated header files.
• Comments in generated files now refer to .cp instead of .c files.
• Cmd-I no longer changes the size of CEditText items.
• CShapeButton unhilites appropriately.
• VA-defined data members of type long can now be properly set in
Pane Info.
• Pane Info is no longer enabled when a view is selected in the
document window.
• Unchecking "use file" for a document now generates compilable
code.
• Identifier in Pane Info is now validated to be <= 31 characters,
a valid C identifier and unique within the view.
• Entering duplicate command names is not allowed.
• Changing the class of a pane while its Pane Info dialog is open
dismisses the dialog (instead of scrambling it or crashing).
• The Pane Info for CArrayPanes no longer includes the number of
columns.
• Deleting a view now forces a Generate All. (The user must still manually
remove the view class from the project, if necessary, but other generated
files will not refer to the class.) If a file is closed with a Generate
All pending, it will be remembered when the file is reopened.
• Opening a file will fail if the file was written by a later version of VA.